feat: SCIM provisioning conflict resolutions - #8344
Merged
Merged
Conversation
…nts that first need to be manually confirmed
Collaborator
🚀 Snapshot Release (
|
| Package | Version | Info |
|---|---|---|
@graphql-hive/apollo |
0.48.4-alpha-20260810132629-e12b9be064427f3c48bd423eed40e94cb763d35b |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/cli |
0.61.4-alpha-20260810132629-e12b9be064427f3c48bd423eed40e94cb763d35b |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/core |
0.22.2-alpha-20260810132629-e12b9be064427f3c48bd423eed40e94cb763d35b |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/envelop |
0.40.9-alpha-20260810132629-e12b9be064427f3c48bd423eed40e94cb763d35b |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/gateway-plugin-console-sdk |
0.1.2-alpha-20260810132629-e12b9be064427f3c48bd423eed40e94cb763d35b |
npm ↗︎ unpkg ↗︎ |
@graphql-hive/yoga |
0.49.2-alpha-20260810132629-e12b9be064427f3c48bd423eed40e94cb763d35b |
npm ↗︎ unpkg ↗︎ |
hive |
11.11.0-alpha-20260810132629-e12b9be064427f3c48bd423eed40e94cb763d35b |
npm ↗︎ unpkg ↗︎ |
Contributor
|
🐋 This PR was built and pushed to the following Docker images: Targets: Platforms: Image Tags: |
n1ru4l
marked this pull request as ready for review
August 9, 2026 22:02
dotansimha
approved these changes
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduces a way of resolving scim provisioning conflicts instead of taking over the accounts immediatly.
When a scim user is provisioned, but it already exists within the organization, the
provisioning_statusof that user is set to'pendingConfirmation'.Internal run through video (UI slightly outdated; the screenshots below are more up 2 date and fix some shortcomings I mentioned before).
The provisioning conflict count is displayed within the user provisioning settings:
The conflict can be resolved via the members UI, which provides a list of all the conflicting users:
The viewer needs to confirm for each of these users that it is now managed via SCIM. Showing the groups and status of the user helps to make a sane decision and avoid accidental lockout.
After confirming all users, we have a proper emtpy state 🥳